Skip to content

chore(release): adopt versionCode scheme and scope signing secrets#28

Merged
Xitee1 merged 1 commit into
mainfrom
chore/release-prep
Apr 18, 2026
Merged

chore(release): adopt versionCode scheme and scope signing secrets#28
Xitee1 merged 1 commit into
mainfrom
chore/release-prep

Conversation

@Xitee1
Copy link
Copy Markdown
Owner

@Xitee1 Xitee1 commented Apr 18, 2026

Summary

  • Switch versionCode to major*100000 + minor*1000 + patch*10 (1.0.0 = 100000), leaving room for minor/patch/hotfix bumps without ever colliding.
  • Bind the release workflow to a new release GitHub Environment so the signing secrets are only injected on v* tag runs, not on PR or branch builds.

Required setup before next release

  • Create environment release in repo settings.
  • Restrict deployment tags: pattern v*.
  • Add the four secrets (SIGNING_KEYSTORE_BASE64, SIGNING_KEYSTORE_PASSWORD, SIGNING_KEY_ALIAS, SIGNING_KEY_PASSWORD) to that environment, not as repository secrets.

Test plan

  • Verify CI still passes on this PR (no signing needed for debug build).
  • After merge, create environment + secrets, then push a v1.0.0 tag and confirm the release workflow signs and attaches the APK.

🤖 Generated with Claude Code

- Switch versionCode to major*100000 + minor*1000 + patch*10 (1.0.0 = 100000)
- Bind release workflow to a `release` GitHub environment so signing
  secrets are only available on v* tag runs, not on PRs/branches

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Xitee1 Xitee1 merged commit f3ad3f1 into main Apr 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant